Reset and replay of memory sub-system controller in a memory sub-system

ABSTRACT

In an embodiment, a system includes a plurality of memory components and a processing device that is operatively coupled with the plurality of memory components. The processing device includes a host interface, an access management component, a media management component (MMC), and an MMC-restart manager that is configured to perform operations including detecting a triggering event for restarting the MMC, and responsively performing MMC-restart operations that include suspending operation of the access management component; determining whether the MMC is operating, and if so then suspending operation of the MMC; resetting the MMC; resuming operation of the MMC; and resuming operation of the access management component.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional PatentApplication Ser. No. 62/874,359, filed Jul. 15, 2019 and entitled “Resetand Replay of a Memory Sub-System Controller in a Memory Sub-System,”the entirety of which is hereby incorporated herein by reference.

TECHNICAL FIELD

Embodiments of the disclosure relate generally to memory sub-systems andmore specifically to reset and replay of a memory sub-system controllerin a memory sub-system.

BACKGROUND

A memory sub-system can be a storage device, a memory module, or ahybrid of a storage device and a memory module. The memory sub-systemcan include one or more memory components that store data. The memorycomponents can be, as examples, non-volatile memory components and/orvolatile memory components. In general, a host system can utilize amemory sub-system to store data at the memory components and to retrievedata from the memory components.

BRIEF DESCRIPTION OF THE DRAWINGS

The disclosure will be understood more fully from the detaileddescription given below and from the accompanying drawings of variousembodiments of the disclosure. The drawings, however, should not betaken to limit the disclosure to the specific embodiments, but are forexplanation and understanding only.

FIG. 1 is a block diagram of an example computing environment thatincludes a host device and a memory sub-system, the memory sub-systemincluding a memory sub-system controller and a plurality of memorydevices, in accordance with some embodiments of the present disclosure.

FIG. 2 is a block diagram of an example media management component ofthe memory sub-system controller of FIG. 1 in accordance with someembodiments of the present disclosure.

FIG. 3 is a flow diagram of an example method for reset and replay of amemory sub-system controller in a memory sub-system that can beperformed by the memory sub-system controller of FIG. 1 in accordancewith some embodiments of the present disclosure.

FIG. 4 is a flow diagram depicting example operations performed by thememory sub-system controller of FIG. 1 in accordance with someembodiments of the present disclosure.

FIG. 5 is a message flow diagram depicting communications among the hostdevice and various functional components of the memory sub-systemcontroller of FIG. 1, as well as operations performed by the memorysub-system controller of FIG. 1, in accordance with some embodiments ofthe present disclosure,

FIG. 6 is a block diagram of an example computer system in whichembodiments of the present disclosure may operate.

DETAILED DESCRIPTION

Implementations of the present disclosure are directed to reset andreplay of a memory sub-system controller in a memory sub-system. Amemory sub-system can be a storage device, a memory module, or a hybridof a storage device and a memory module. Examples of storage devices andmemory modules are described below in connection with FIG. 1. Ingeneral, a host system can utilize a memory sub-system that includes oneor more memory components (also referred to herein as “memory devices”).The host system can provide data to be stored at the memory sub-systemand can request data to be retrieved from the memory sub-system.

The host system can send access requests to the memory sub-system, suchas to store data at the memory sub-system and to read data from thememory sub-system. The data to be read and written are hereinafterreferred to as “user data”. A host request can include a logical address(e.g., logical block address (LBA)) for the user data, which is thelocation the host system associates with the user data. The logicaladdress (e.g., LBA) can be part of metadata for the user data.

A data path refers to the logical course or path that user data andmetadata follow as they move throughout the memory sub-system. The datapath in the memory sub-system handles read and write data commandsreceived from the host system. The data path encompasses the complete,end-to-end course taken by data as it is either written to or read fromthe underlying memory devices.

A control path refers to the logical course or path that providesdifferent control signals, for example, to components on the data pathto control how the data path works properly. The control path and datapath include digital circuitry, registers, and interconnecting buses.

Operational errors, system failures, and/or the like occur from time totime with respect to memory sub-systems. It can be evident from theperspective of a host system that an event such as this has occurred inconnection with a memory sub-system if the memory sub-system reports theoccurrence of an error, an exception, an assertion, a condition (e.g.,high temperature), and/or the like to the host system, or if the memorysub-system fails to meet one or more performance metrics. In some cases,a host system can become aware of a problem with a memory sub-systemwhen the host system receives a hardware interrupt from thememory-sub-system. In other instances, a host system may become aware ofa problem with a memory sub-system if the memory sub-system becomesunresponsive, goes offline, becomes disabled, and/or the like.

In some cases, a host system may attempt to restart a memory sub-system,perhaps after expiration of a timeout period during which the hostsystem was waiting for the memory sub-system to respond. Moreover, if ahost system has to restart a memory sub-system more than a thresholdnumber of times or, perhaps, more than a threshold number of timeswithin a certain amount of time, as examples, the host system mayconsider the memory sub-system to be unreliable, defective, and/or thelike. In such instances, the host system may disable and/or discontinueuse of the memory sub-system, as examples.

Implementations of the present disclosure address the above and otherdeficiencies with reset and/or replay of a memory sub-system controllerin a memory sub-system. In accordance with at least one implementation,a memory sub-system controller of a memory sub-system includes amedia-management-component restart (MMC-restart) manager, which invarious different embodiments could be implemented in any combination offirmware, software, and hardware. The hardware can be part of the memorysub-system controller. The hardware can include a digital circuitry withdedicated (i.e., hard-coded) logic to perform the operations describedherein. In some embodiments that are described herein, the MMC-restartmanager is implemented in firmware. Functionally, in at least someimplementations, the MMC-restart manager detects what is referred toherein as a triggering event for restarting a functional component ofthe memory sub-system controller that is known as the media managementcomponent. These triggering events are also referred to herein at timesas MMC-restart triggering events, or simply as triggers.

In various different implementations, the triggers can take variousforms. In some cases, one or more of the triggers involves notificationof a problem (e.g., an error) by a component of the memory sub-systemcontroller such as the media management component or another componentknown as the access management component, which resides between the hostinterface and the media management component, and performs operationsincluding queuing commands and buffering data both from the host deviceto the media management component and vice versa. detecting a lack ofcommunication with, e.g., the media management component for more than apredetermined amount of time. Other example triggers are describedthroughout the present disclosure.

In response to detecting one or more triggers, in at least someimplementations of the present disclosure, the MMC-restart managerperforms a set of operations that are referred to herein at times asMMC-restart operations, in some implementations, the MMC-restartoperations include operations that individually and/or collectivelysuspend the memory sub-system serving the host device (e.g., receivingsubmitted commands from the host device, returning completed commands tothe host device, receiving write data from the host device and writingthat data to one or more of the memory devices of the memory sub-system,returning requested data that is read from one or more of the memorydevices to the host device, and/or the like). In at least someinstances, upon completion of the MMC-restart operations, the memorysub-system resumes serving the host device.

The MMC-restart operations could include operations such as suspendingoperation of the access management component; resetting the mediamanagement component; determining whether the media management componentis operating, and if so then suspending operation of the mediamanagement component; resuming operation of the media managementcomponent; and resuming operation of the access management component. Insome instances, the MMC-restart operations also include resetting andrestarting one or more operations that are pending in the accessmanagement component; in some such cases, the MMC-restart operationsalso include reordering pending operations in the access managementcomponent. Further details regarding these example MMC-restartoperations are given throughout this disclosure, and other exampleMMC-restart operations are described as well.

Among the benefits of implementations of the present disclosure is thata memory sub-system self recovers from internal problems, perhapswithout an associated host device detecting that a problem (e.g., adelay) had occurred. Moreover, whether or not the host device haddetected that a problem had occurred in connection with the memorysub-system, implementations of the present disclosure prevent the hostdevice from having to reset the memory sub-system in order to continueoperation. Additionally, to the extent the host device keeps count ofsuch occurrences, the memory sub-system being able to prevent suchoccurrences keeps such a count from increasing. Thus, the host device isless likely to consider the memory sub-system to be problematic,defective, and/or the like, and is less likely to take measures such asdisabling and/or discontinuing use of the memory sub-system. Otherbenefits will be evident to those of skill in the relevant art havingthe benefit of this disclosure.

FIG. 1 illustrates an example computing environment 100 that includes amemory sub-system 110 in accordance with some embodiments of the presentdisclosure. The memory sub-system 110 can include media, such as one ormore volatile memory devices (e.g., memory device 140), one or morenon-volatile memory devices (e.g., memory device(s) 130), or acombination of such.

A memory sub-system 110 can be a storage device, a memory module, or ahybrid of a storage device and a memory module. Examples of a storagedevice include a solid-state drive (SSD), a flash drive, a universalserial bus (USB) flash drive, an embedded. Multi-Media Controller (eMMC)drive, a Universal Flash Storage (UFS) drive, and a hard disk drive(HDD). Examples of memory modules include a dual in-line memory module(DIMM), a small outline DIMM (SO-DIMM), and a non-volatile dual in-linememory module (NVDIMM).

The computing environment 100 can include a host system 120 that iscoupled to a memory system. The memory system can include one or morememory sub-systems 110. In some embodiments, the host system 120 iscoupled to different types of memory sub-system 110. FIG. 1 illustratesan example of the host system 120 coupled to one memory sub-system 110.The host system 120 uses the memory sub-system 110, for example, towrite user data to the memory sub-system 110 and read user data from thememory sub-system 110. As used herein, “coupled to” generally refers toa connection between components, which can be an indirect communicativeconnection or direct communicative connection (e.g., without interveningcomponents), whether wired or wireless, including connections such aselectrical, optical, magnetic, etc.

The host system 120 can be a computing device such as a desktopcomputer, laptop computer, network server, mobile device, embeddedcomputer (e.g., one included in a vehicle, industrial equipment, or anetworked commercial device), or such computing device that includes amemory and a processing device. The host system 120 can be coupled tothe memory sub-system 110 via a physical host interface. Examples of aphysical host interface include, but are not limited to, a serialadvanced technology attachment (SATA) interface, a peripheral componentinterconnect express (PCIe) interface, universal serial bus (USB)interface, Fibre Channel, Serial Attached SCSI (SAS), etc. The physicalhost interface can be used to transmit data (e.g., user data) betweenthe host system 120 and the memory sub-system 110. The host system 120can further utilize a non-volatile memory express (NVMe) interface toaccess the memory components (e.g., the memory devices 130) when thememory sub-system 110 is coupled with the host system 120 by a PCIeinterface. The physical host interface can provide an interface forpassing control, address, user data, and other signals between thememory sub-system 110 and the host system 120.

The memory devices can include any combination of the different types ofvolatile memory devices and/or non-volatile memory devices. The volatilememory devices (e.g., memory device 140) can be, but are not limited to,RAM, such as DRAM and synchronous DRAM (SDRAM).

An example of non-volatile memory devices (e.g., the memory device 130)includes three-dimensional (3D) cross-point (“3D cross-point”) typeflash memory, which is a cross-point array of non-volatile memory cells.A cross-point array of non-volatile memory can perform bit storage basedon a change of bulk resistance, in conjunction with a stackablecross-gridded data access array. Additionally, in contrast to manyflash-based memories, cross-point non-volatile memory can perform awrite in-place operation, where a non-volatile memory cell can beprogrammed without the non-volatile memory cell being previously erased.

Although non-volatile memory components such as 3D cross-point typememory are described, the memory device 130 can be based on any othertype of non-volatile memory, such as negative-and (NAND), read-onlymemory (ROM), phase change memory (PCM), self-selecting memory, otherchalcogenide based memories, ferroelectric random access memory (FeRAM),magneto random access memory (MRAM), negative-or (NOR) flash memory, andelectrically erasable programmable read-only memory (EEPROM).

In some embodiments, each of the memory devices 130 can include one ormore arrays of memory cells such as single level cells (SLCs),multi-level cells (MLCs), triple level cells (TLCs), quad-level cells(QLCs), or a combination of such. In some embodiments, a particularmemory component can include an SLC portion and/or an MLC portion (e.g.,a TLC portion or a QLC portion) of memory cells. Each of the memorycells can store one or more bits of data used by the host system 120.Furthermore, the memory cells of the memory devices 130 can be groupedas memory pages or memory blocks that can refer to a unit of the memorycomponent used to store data.

The memory sub-system controller 115 can communicate with the memorydevices 130 to perform operations such as reading data, writing data, orerasing data at the memory devices 130, and other such operations. Thememory sub-system controller 115 can include hardware such as one ormore integrated circuits and/or discrete components, a buffer memory, ora combination thereof. The memory sub-system controller 115 can be amicrocontroller, special purpose logic circuitry (e.g., a fieldprogrammable gate array (FPGA), an application specific integratedcircuit (ASIC), etc.), or another suitable processor.

Furthermore, in some implementations, the memory sub-system controller115 includes a processor (processing device) 117 configured to executeinstructions stored in local memory 119. In the illustrated example, thelocal memory 119 of the memory sub-system controller 115 includes anembedded memory configured to store instructions for performing variousprocesses, operations, logic flows, and routines that control operationof the memory sub-system 110, including handling communications betweenthe memory sub-system 110 and the host system 120.

In some embodiments, the local memory 119 includes memory registersstoring memory pointers, fetched data, etc. The local memory 119 canalso include ROM for storing microcode. While the example memorysub-system 110 in FIG. 1 is illustrated as including the memorysub-system controller 115, in another embodiment of the presentdisclosure, a memory sub-system 110 may not include a memory sub-systemcontroller, and may instead rely upon external control (provided, by,e.g., an external host or a processor or controller separate from thememory sub-system 110).

In general, the memory sub-system controller 115 can receive commands oroperations from the host system 120 and can convert the commands oroperations into instructions or appropriate commands to achieve thedesired access to the memory devices 130. The memory sub-systemcontroller 115 can be responsible for other operations such aswear-leveling operations, garbage-collection operations, error-detectionand error-correcting-code (ECC) operations, encryption operations,caching operations, and address translations between a logical address(e.g., logical block address (LBA)) and a physical address that areassociated with the memory devices 130. The memory sub-system controller115 can further include a host interface 125 to communicate with thehost system 120 via the physical host interface. The host interface 125can convert the commands received from the host system 120 into commandinstructions to access the memory devices 130, as well as convertresponses associated with the memory devices 130 into information forthe host system 120.

The memory sub-system 110 can also include additional circuitry orcomponents that are not illustrated. In some embodiments, the memorysub-system 110 can include a cache or buffer (e.g., DRAM) and addresscircuitry (e.g., a row decoder and a column decoder) that can receive anaddress from the memory sub-system controller 115 and decode the addressto access the memory devices 130.

In some embodiments, the memory devices 130 include local mediacontrollers 135 that operate in conjunction with memory sub-systemcontroller 115 to execute operations on one or more memory cells of thememory devices 130. An external controller (e.g., memory sub-systemcontroller 115) can externally manage the media device 130 (e.g.,perform media management operations on the media device 130). In someembodiments, the memory devices 130 can be locally managed memorydevices, which is a raw memory device combined with a local mediacontroller 135 that performs memory management operations on the memorydevice 130 within the same memory device package.

The memory sub-system controller 115 can include a media managementcomponent 121 that interfaces between the memory sub-system controller115 and the memory devices 130. Additionally, the memory sub-systemcontroller 115 can include access management component 123, whichinterfaces between the host interface 125 and the media managementcomponent 121. In As described above, in at least one implementation ofthe present disclosure, among other functions, the access managementcomponent 123 provides queuing of commands and buffering of data in bothdirections between the host device 120 and the media managementcomponent 121. Within the memory sub-system controller 115, thesefunctions of the access management component 123 take the form of theaccess management component 123 providing queuing of commands andbuffering of data in both directions between the host interface 125 andthe media management component 121, as described more fully below inconnection with FIG. 2.

In at least one implementation of the present disclosure, and as is alsodepicted in FIG. 1, the memory sub-system controller 115 can alsoinclude an MMC-restart manager 113. In various differentimplementations, the MMC-restart manager 113 can take the form of orinclude circuitry, dedicated logic, programmable logic, firmware,software, and/or the like for performing at least the MMC-restartoperations described herein. As mentioned above, by way of example andnot limitation, the MMC-restart manager 113 is primarily describedherein as being implemented in firmware.

In some instances, the memory sub-system controller 115 includes atleast a portion of the MMC-restart manager 113 the processor 117 can beconfigured to execute instructions stored in the local memory 119 forperforming one or more of the MMC-restart operations described herein.In some embodiments, the MMC-restart manager 113 is part of the hostsystem 120, an application, or an operating system. Various functionsthat are performed by the MMC-restart manager 113 in differentcombinations in different embodiments are described throughout thisdisclosure, as are example communications among entities such as thehost system 120, the host interface 125, the access management component123, the media management component 121, and the MMC-restart manager113.

FIG. 2 depicts an example system architecture 200 in accordance withsome embodiments of the present disclosure. The architecture 200 isprovided by way of example and not limitation. In addition to the memorysub-system controller 115, also depicted in FIG. 2 is the host system120. Any of the components of the memory sub-system controller 115 thatare depicted in FIG. 2, or any of the sub-components thereof, can berealized using software and/or firmware executing on hardware, or ashardware circuits. As one example, one or more of the components orsub-components could be realized as programmed sections of an FPGA.

Moreover, some components of the memory sub-system controller 115 thatare depicted in FIG. 1 are not depicted in FIG. 2: the processor 117 andthe local memory 119. Also not depicted in FIG. 2 are connections orcommunications between the memory sub-system controller 115 and thememory devices 130 (e.g., between the media management component 121 andthe memory devices 130). These omissions are not to imply that suchcomponents and connections are not present in at least someimplementations, but rather are intended to more clearly present theentities, components, connections, communications, and the like that aredepicted in FIG. 2. The media management component 121 includes varioushardware sub-components that includes digital circuitry with dedicated(i.e., hard-coded) logic to perform the operations of the componentsdescribed herein.

The media management component can include digital and analog circuitryto define a control path and a data path or portions of a control pathand a data path. A data path refers to the logical course or path thatuser data and metadata follow as they move throughout the memorysub-system. The data path in the memory sub-system handles read andwrite data commands received from the host system. The data pathencompasses the complete, end-to-end course taken by data as it iseither written to or read from the underlying memory devices. A controlpath refers to the logical course or path that provides differentcontrol signals, for example, to components on the data path to controlhow the data path works properly. The control path and data path includedigital circuitry, registers, and interconnecting buses.

The media management component 121 is depicted in the architecture 200of FIG. 2 as including a configuration-and-status circuit 202, a controlpath 204, and a data path 206. The configuration-and-status circuit 202can receive configuration and status requests from, and can transmitconfiguration and status responses to, the processor 117. Theconfiguration and status requests could relate to the processor 117configuring various operational parameters of the media managementcomponent 121, and could also relate to the processor 117 requestingstatus information regarding the media management component 121. Theconfiguration and status responses could include responses to thosestatus requests, as well as confirmation (or failure) responsesregarding any received configuration requests.

The control path 204 is depicted in FIG. 2 as including control-pathmemory 215, resettable registers 216, and sticky registers 218.

Although not pictured in FIG. 2, the control path 204 could also includesequential control-path stages for performing operations such as parsingcommands, processing commands, and completing commands. With respect tocompleting commands, this can include the control path 204 formulatingresponses to commands, indicating success or failure with respect toexecution of the commands, and transmitting those responses to theaccess management component 123 for intended receipt by the host system120.

The control-path memory 215 could be static RAM (SRAM) as one example,and could be used by the data path 206 to store any data used by thedata path 206 during operation.

In at least one implementation of the present disclosure, the resettableregisters 216 include one or more registers that, when the mediamanagement component 121 undergoes a reset operation, have any valuesstored therein cleared. Moreover, in at least one implementation, thesticky registers 218 include one or more registers that, when the mediamanagement component 121 undergoes a reset operation, do not have anyvalues stored therein cleared—rather, any values stored in one or moreof the sticky registers 218 persist through a reset of the mediamanagement component 121. In at least one implementation, any valuesstored in either or both of the resettable registers 216 and the stickyregisters 218 do not persist through a power cycle of the mediamanagement component 121, which could occur as part of a power cycle ofthe memory sub-system controller 115, as an example.

As a general matter, the data path 206 may function to execute somecommands (e.g., data requests such as write requests, read requests,and/or the like) that originate at the host system 120, includingexecuting those data requests vis-à-vis the memory devices 130. In theexample architecture 200 that is depicted in FIG. 2, the data path 206is shown as including a data buffer 220. In the case of write requests,the data path 206 may buffer write-data segments, which contain datafrom the host system 120 that is to be written to one or more of thememory devices 130, in the data buffer 220 prior to writing thosewrite-data segments to one or more of the memory devices 130. In thecase of read requests, the data path 206 may buffer read-data segments,which contain data that has been read from one or more of the memorydevices 130 at the request of the host system 120, prior to transmittingthose read-data segments to the access management component 123 forintended receipt by the host system 120. In some implementations, thedata buffer 220 is a single buffer; in other implementations, the databuffer 220 includes multiple data buffers (e.g., a write-data buffer anda read-data buffer).

As depicted in FIG. 2, the access management component 123 includes acommand-submission queue 208, a command-completion queue 210, a writebuffer 212, and a read buffer 214, each of which may be arranged tooperate in a first-in-first-out (FIFO) manner, though otherimplementations could be selected instead for one or more of thesequeues and/or buffers. Both the command-submission queue 208 and thecommand-completion queue 210 are arranged in at least one implementationto function as queues for commands between the host interface 125 andthe media management component 121. Furthermore, both the write buffer212 and the read buffer 214 are arranged in at least one implementationto function as buffers for data segments (e.g., blocks, pages, packets,frames, and/or any other suitable quantities of data) in between thehost interface 125 and the media management component 121.

In operation, in at least one implementation of the present disclosure,the host interface 125 receives, from the host system 120, submittedhost commands 230, which could include write commands, read commands,erase commands, reset commands, power-cycle commands, and/or any othertype of commands that the host system 120 may transmit to the memorysub-system 110. The host interface 125 can convert the submitted hostcommands 230 into submitted host-interface commands 232. In someimplementations, this conversion involves the host interface 125reformatting the submitted host commands 230 into the submittedhost-interface commands 232, which may be in a format suitable forinternal processing by the memory sub-system controller 115. The hostinterface 125 transmits the submitted host-interface commands 232 to thecommand-submission queue 208. When the submitted host-interface commands232 emerge from the command-submission queue 208, they are referred toherein as submitted access management component commands 234, which aretransmitted from the command-submission queue 208 to the control path204.

As can be seen in the preceding paragraph, the convention used in thisdescription for the various commands, write-data segments, and read-datasegments that are depicted in and described in connection with FIG. 2 isto name the commands, write-data segments, and read-data segmentsaccording to which entity is generating (or at least transmitting) them.Continuing this description, then, it can be seen that the control path204 transmits completed MMC commands 240 to the command-completion queue210. When the completed MMC commands 240 emerge from thecommand-completion queue 210, they are referred to herein as completedaccess-management-component commands 242, which are transmitted from thecommand-completion queue 210 to the host interface 125. In at least oneimplementation, the host interface 125 converts the completedaccess-management-component commands 242 into a format that is suitablefor transmission to and processing by the host system 120. Thoseconverted and transmitted commands are referred to herein as completedhost-interface commands 244.

Moreover, the host interface 125 receives host write-data segments 250from the host system 120. The host write-data segments 250 include datathat the host system 120 is requesting be written to one or more of thememory devices 130. The host interface 125 receives the host write-datasegments 250, converts them into a format that is suitable for internalprocessing by the memory sub-system 110, and transmits the convertedwrite-data segments to the write buffer 212 as host-interface write-datasegments 252. When the host-interface write-data segments 252 emergefrom the write buffer 212, they are referred to herein asaccess-management-component write-data segments 254, which aretransmitted from the write buffer 212 of the access management component123 to the data path 206. The access-management-component write-datasegments 254 may then be buffered in the data buffer 220 prior to beingwritten to one or more of the memory devices 130.

In the other direction, as described above, the data path 206 may usethe data buffer 220 to buffer read-data segments that have been readfrom one or more of the memory devices 130. When they emerge from thedata buffer 220 and are transmitted by the data path 206 to the readbuffer 214 of the access management component 123, these read-datasegments are referred to herein as the MMC read-data segments 260. Andwhen the MMC read-data segments 260 emerge from the read buffer 214,they are referred to herein as the access-management-component read-datasegments 262, which are transmitted from the read buffer 214 of theaccess management component 123 to the host interface 125. In at leastone implementation, the host interface 125 converts theaccess-management-component read-data segments 262 into a format that issuitable for transmission to and processing by the host system 120.These converted and transmitted read-data segments are referred toherein as the host-interface read-data segments 264.

FIG. 3 is a flow diagram of an example method 300 for reset and replayof a memory sub-system controller in accordance with some embodiments ofthe present disclosure. The method 300 can be performed by processinglogic that can include hardware (e.g., processing device, circuitry,dedicated logic, programmable logic, microcode, hardware of a device,integrated circuit, etc.), software (e.g., instructions run or executedon a processing device), or a combination thereof. In some embodiments,the method 300 is performed by the restart manager 113 of FIG. 1.Although shown in a particular sequence or order, unless otherwisespecified, the order of the operations can be modified. Thus, theillustrated embodiments should be understood only as examples, and theillustrated operations can be performed in a different order, and someoperations can be performed in parallel. Additionally, one or moreoperations can be omitted in various embodiments. Thus, not alloperations are required in every embodiment. Other operation flows arepossible.

At operation 302, the processing device detects a triggering event, suchas an error. Examples of errors include, and are not limited to, errorsat a media management component of the memory sub-system controller,errors related to one or more of the memory devices 130, uncorrectabledata errors pertaining to attempts to read data from one or more of thememory devices 130, and detecting at least a threshold drop in athroughput level of the memory sub-system or one or more components ofthe memory sub-system. Errors at the media management component of thememory sub-system can include internal errors such as internal logicerrors, errors related to changes in voltage and/or frequency, anderrors that occur in SRAM and/or registers, as well as logic designerrors.

The processing device can detect an error by receiving a signal. Thesignal can be received, for example, as an interrupt signal. Theinterrupt signal can be received from firmware being executed, forexample, by the processing device.

At operation 304, the processing device prevents receiving any incomingcommands from a host interface (e.g., the host interface 125). A memorysub-system can receive host commands from a host system via a hostinterface. The processing device can receive commands from the hostinterface. The processing device can suspend acceptance of hostinterface command traffic from the host interface. Two examples ofhost-interface traffic that the access management component 123 could besuspended from accepting are the submitted host-interface commands 232and the host-interface write-data segments 252.

At operation 306, the processing device determines whether a mediamanagement component of the memory sub-system controller is active. Thedetermination can be based, for example, on whether or not the mediamanagement component is performing operations or particular operations(e.g., processing incoming commands). If the media management componentis active, the processing device suspends operation of the mediamanagement component, for example by suspending acceptance by the mediamanagement component of incoming command traffic (e.g.,access-management-component traffic). Some examples ofaccess-management-component traffic—that the media management component121 could be suspended from accepting—are the submittedaccess-management-component commands 234 and theaccess-management-component write-data segments 254.

At operation 308, the processing device resets the media managementcomponent. As described herein, in some implementations, the mediamanagement component 121 includes the control path 204, which includesthe control-path memory 215 and the one or more resettable registers216, as well as the data path 206, which includes the data buffer 220.In some instances of performing the operation 308, the MMC-restartmanager 113 clears the control-path memory 215, clears the resettableregisters 216, and clears the data buffer 220. It is noted that“clearing” in this context can also be referred to as “cleaning.”

Another example MMC-restart operation is shown at operation 310, whichinvolves the MMC-restart manager 113 resuming operation of the mediamanagement component 121. In some instances, this can involve theMMC-restart manager 113 and/or another entity in the memory sub-systemcontroller 115 sending the media management component 121 an instructionto resume operation, which could involve resuming the acceptance ofaccess-management-component traffic from the access management component123.

The MMC-restart operations could also include the MMC-restart manager113 resuming operation of the access management component 123 (seeoperation 312). This could involve the MMC-restart manager 113 and/oranother entity in the memory sub-system controller 115 sending theaccess management component 123 an instruction to resume operation,which could include resuming the acceptance of host-interface trafficfrom the host interface 125.

In some implementations of the present disclosure, after suspendingoperation of the access management component 123 (at operation 304) andprior to resuming operation of the access management component 123 (atoperation 312), the MMC-restart manager 113 performs an additional setof MMC-restart operations that involves the MMC-restart manager 113determining whether there are any pending commands in the accessmanagement component 123 (e.g., in the command-submission queue 208),and if so then resetting a state of, as well as restarting, each suchpending command in the access management component 123. In someinstances, restarting each pending command in the access managementcomponent 123 involves restarting a group of pending commands in theaccess management component 123 in the order in which they were queuedin the command-submission queue 208 prior to the suspension of theaccess management component 123 (at operation 304). In other instances,however, the MMC-restart manager 113 reorders a group of pendingcommands that are queued in the command-submission queue 208 in theaccess management component 123 into a revised order, and then restartsthat group of pending commands in that revised order.

FIG. 4 is a flow diagram of an example method 400 for reset and replayof a memory sub-system controller in accordance with some embodiments ofthe present disclosure. The method 400 can be performed by processinglogic that can include hardware (e.g., processing device, circuitry,dedicated logic, programmable logic, microcode, hardware of a device,integrated circuit, etc.), software (e.g., instructions run or executedon a processing device), or a combination thereof. In some embodiments,the method 400 is performed by the restart manager 113 of FIG. 1.Although shown in a particular sequence or order, unless otherwisespecified, the order of the operations can be modified. Thus, theillustrated embodiments should be understood only as examples, and theillustrated operations can be performed in a different order, and someoperations can be performed in parallel. Additionally, one or moreoperations can be omitted in various embodiments. Thus, not alloperations are required in every embodiment. Other operation flows arepossible.

A number of the operations that are performed as part of the method 400are similar to operations that are performed as part of the method 300,and therefore are not described in connection with the method 400 in asgreat of detail.

At operation 402, with the MMC-restart manager 113 polling (e.g.,checking) for the occurrence of an MMC-restart trigger. Control thenproceeds to operation 404, where the MMC-restart manager 113 evaluateswhether or not it has in fact detected such a triggering event. If not,control returns to operation 402 and the MMC-restart manager 113continues polling. If so, however, control proceeds to operation 406,where the MMC-restart manager 113 suspends the access managementcomponent 123.

Control then proceeds to the operation 408, at which the MMC-restartmanager 113 determines whether or not the media management component 121is currently operating. The MMC-restart, manager 113 may make thisdetermination based on an elapsed time since last receiving anycommunication from the media management component 121. In other cases,the MMC-restart manager 113 may make this determination by activelysending a ping message to the media management component 121 andawaiting a response. If a response is received within a certain amountof time, the MMC-restart manager 113 may determine that the mediamanagement component 121 is operating. If no such response is receivedwithin that predetermined amount of time, the MMC-restart manager 113may determine that the media management component 121 is not operating.

If the MMC-restart manager 113 determines at operation 408 that themedia management component 121 is operating, then control proceeds tooperation 410, at which the MMC-restart manager 113 suspends the mediamanagement component 121. Control then proceeds from operation 410 tooperation 412. If, instead, the MMC-restart manager 113 determines atoperation 408 that the media management component 121 is not operating,then control proceeds directly from operation 408 to operation 412.Either way, at operation 412, the MMC-restart manager 113 resets themedia management component 121. Control then proceeds to operation 414,at which the MMC-restart manager 113 resumes operation of the mediamanagement component 121.

Next, at operation 416, the MMC-restart manager 113 evaluates whether ornot there are any pending commands in the access management component123 (e.g., queued in the command-submission queue 208). If so, controlproceeds to operation 418, at which the MMC-restart manager 113 resetseach such pending command, and then to operation 420, at which theMMC-restart manager 113 restarts each such pending command. Control thenproceeds to operation 422. If, instead, the MMC-restart manager 113determines at operation 416 that there are no pending commands in theaccess management component 123, control proceeds directly fromoperation 416 to operation 422. Either way, at operation 422, theMMC-restart manager 113 resumes operation of the access managementcomponent 123. Control then returns to operation 402, at which theMMC-restart manager 113 polls the occurrence of one or more MMC-restarttriggers.

A number of the communications and operations that are described hereinare displayed in graphical form in an example message flow 500 that isdepicted in and described here in connection with FIG. 5. As is the casewith the method 400 of FIG. 4, these communications and operations arenot described in connection with FIG. 5 in as great of detail as theyare elsewhere in this disclosure. The message flow 500 does, however,provide additional visualizable understanding of at least someimplementations of the present disclosure.

It can be seen that the entities that are represented in the messageflow 500 are the host system 120, the host interface 125, theMMC-restart manager 113, the access management component 123 (includingthe command-submission queue 208, the command-completion queue 210, thewrite buffer 212, and the read buffer 214), and the media managementcomponent 121 (including the control path 204 and the data path 206).Moreover, it can be seen that, during an initial stage 502, the messageflow 500 begins with normal operation as between the host system 120 andthe memory sub-system 110. As part of this normal operation, the memorysub-system 110 is serving host requests from the host system 120.

In particular, it can be seen during the initial stage 502 that the hostsystem 120 sends the submitted host commands 230 to the host interface125, which in turn sends the submitted host-interface commands 232 tothe command-submission queue 208. These commands emerge from thecommand-submission queue 208 as the submittedaccess-management-component commands 234, which are transmitted to thecontrol path 204. Furthermore, the control path 204 sends the completedMMC commands 240 to the command-completion queue 210. The commands thatemerge from the command-completion queue 210 are the completedaccess-management-component commands 242, which are transmitted by thecommand-completion queue 210 to the host interface 125, which in turntransmits the completed host-interface commands 244 to the host system120.

Additionally, the host system 120 sends the host write-data segments 250to the host interface 125, which in turn sends the host-interfacewrite-data segments 252 to the write buffer 212. The write buffer 212then sends the access-management-component write-data segments 254 tothe data path 206. Moreover, the data path 206 sends the MMC read-datasegments 260 to the read buffer 214, which in turn sends theaccess-management-component read-data segments 262 to the host interface125. The host interface 125 then sends the host-interface read-datasegments 264 to the host system 120.

In summary, then, it can be seen during the initial stage 502 thatcommands and data-segments are being exchanged between the host system120 and the memory sub-system 110 (in that commands and data segmentsare being exchanged between the host system 120 and the host interface125 of the memory sub-system controller 115, which is part of the memorysub-system 110). The depicted commands that are being exchanged are thesubmitted host commands 230 and the completed host-interface commands244. The depicted data segments that are being exchanged are the hostwrite-data segments 250 and the host-interface read-data segments 264.

Then, at operation 504, the MMC-restart manager 113 detects anMMC-restart trigger. Next, the MMC-restart manager 113 sends a command506 to the access management component 123 to suspend the accessmanagement component 123. At operation 508, represented by adouble-ended arrow, the MMC-restart manager 113 checks whether or notthe media management component 121 is operating. In this example, theMMC-restart manager 113 determines at operation 508 that the mediamanagement component 121 is operating, and accordingly sends a command510 to the media management component 121 to suspend the mediamanagement component 121. The MMC-restart manager 113 then sends acommand 512 to the media management component 121 to reset the mediamanagement component 121, followed by a command 514 to the mediamanagement component 121 to instruct the media management component 121to resume operation.

After sending the commands 510, 512, and 514, the MMC-restart manager113 (at operation 516, also represented by a double-ended arrow) checkswhether or not there are any pending commands in the access managementcomponent 123 (e.g., queued in the command-submission queue 208). Inthis example, there are some such pending commands, and operation 516therefore also includes the MMC-restart manager 113 resetting andrestarting (perhaps after reordering) those pending commands. Next, theMMC-restart manager 113 sends a command 518 to the media managementcomponent 121, instructing the media management component 121 to resumeoperation.

Finally, it can be seen in the message flow 500 that, at a post-restartstage 520, the memory sub-system 110 is again serving host requests withrespect to the host system 120. This is represented in the message flow500 by the double-ended, end-to-end arrow associated with thepost-restart stage 520. Notably, while there is communication betweenthe host system 120 and the memory sub-system 110 (and in particular thehost interface 125) during the initial stage 502 and again during thepost-restart stage 520, there is no communication between the hostsystem 120 and the memory sub-system 110 in between the initial stage502 and the post-restart stage 520. In at least some such exampleinstances, however, the host system 120 did not need to act to, e.g.,reset or restart the memory sub-system 110. Instead, in accordance withimplementations of the present disclosure, the memory sub-system 110detected and recovered from its own internal issue(s), problem(s),error(s), delay(s), and/or the like.

Moreover, for testing purposes, some implementations of the presentdisclosure include the disposition of one or more functional modulesthat could be implemented using software and/or firmware executing onhardware, or perhaps be implemented as hardware components in or incommunication with the memory sub-system controller 115. Such functionalmodules could operate to intentionally “inject” errors at the mediamanagement component 121 in order to intentionally cause the MMC-restartmanager 113 to detect one or more MMC-restart triggering events, so asto evaluate the performing of one or more of the herein-describedMMC-restart operations. Metrics such as data integrity, the duration oftime in which traffic between the host system 120 and the memorysub-system 110 is suspended, and/or the like could be evaluated usingsuch an approach.

FIG. 6 illustrates an example machine of a computer system 600 withinwhich a set of instructions 626, for causing the machine to perform anyone or more of the methodologies discussed herein, can be executed. Insome embodiments, the computer system 600 can correspond to a hostsystem (e.g., the host system 120 of FIG. 1) that includes, is coupledto, or utilizes a memory sub-system (e.g., the memory sub-system 110 ofFIG. 1) or can be used to perform the operations of a controller (e.g.,to execute an operating system to perform operations corresponding tothe MMC-restart manager 113 of FIG. 1). In alternative embodiments, themachine can be connected (e.g., networked) to other machines in a localarea network (LAN), an intranet, an extranet, and/or the Internet. Themachine can operate in the capacity of a server or a client machine in aclient-server network environment, as a peer machine in a peer-to-peer(or distributed) network environment, or as a server or a client machinein a cloud computing infrastructure or environment.

The machine can be a personal computer (PC), a tablet PC, a set-top box(STB), a personal digital assistant (PDA), a cellular telephone, a webappliance, a server, a network router, a switch or bridge, or anymachine capable of executing a set of instructions (sequential orotherwise) that specify actions to be taken by that machine. Further,while a single machine is illustrated, the term “machine” shall also betaken to include any collection of machines that individually or jointlyexecute a set (or multiple sets) of instructions to perform any one ormore of the methodologies discussed herein.

The example computer system 600 includes a processing device 602, a mainmemory 604 (e.g., ROM, flash memory, DRAM such as SDRAM or RDRAM, etc.),a static memory 606 (e.g., flash memory, SRAM, etc.), and a data storagesystem 618, which communicate with each other via a bus 630.

The processing device 602 represents one or more general-purposeprocessing devices such as a microprocessor, a central processing unit(CPU), or the like. More particularly, the processing device 602 can bea complex instruction set computing (CISC) microprocessor, a reducedinstruction set computing (RISC) microprocessor, a very long instructionword (VLIW) microprocessor, or a processor implementing otherinstruction sets, or processors implementing a combination ofinstruction sets. The processing device 602 can also be one or morespecial-purpose processing devices such as an ASIC, an FPGA, a digitalsignal processor (DSP), a network processor, or the like. In at leastone embodiment, the processing device 602 is configured to executeinstructions 626 for performing the operations discussed herein. Thecomputer system 600 can further include a network interface device 608to communicate over a network 620.

The data storage system 618 can include a machine-readable storagemedium 624 (also known as a computer-readable medium) on which is storedone or more sets of instructions 626 or software embodying any one ormore of the methodologies or functions described herein. Theinstructions 626 can also reside, completely or at least partially,within the main memory 604 and/or within the processing device 602during execution thereof by the computer system 600, the main memory 604and the processing device 602 also constituting machine-readable storagemedia. The machine-readable storage medium 624, data storage system 618,and/or main memory 604 can correspond to the memory sub-system 110 ofFIG. 1.

In an embodiment, the instructions 626 include instructions to implementfunctionality corresponding to an MMC-restart manager 113 (e.g., theMMC-restart manager 113 of FIG. 1). While the machine-readable storagemedium 624 is shown in an example embodiment to be a single medium, theterm “machine-readable storage medium” should be taken to include asingle medium or multiple media that store the one or more sets ofinstructions. The term “machine-readable storage medium” should also betaken to include any medium that is capable of storing or encoding a setof instructions for execution by the machine and that cause the machineto perform any one or more of the methodologies of the presentdisclosure. The term “machine-readable storage medium” shall accordinglybe taken to include, but not be limited to, solid-state memories,optical media, and magnetic media.

Some portions of the preceding detailed description have been presentedin terms of algorithms and symbolic representations of operations ondata bits within a computer memory. These algorithmic descriptions andrepresentations are the ways that are used by those skilled in thedata-processing arts to most effectively convey the substance of theirwork to others skilled in such arts. An algorithm is here, andgenerally, conceived to be a self-consistent sequence of operationsleading to a desired result. The operations are those requiring physicalmanipulations of physical quantities. Usually, though not necessarily,these quantities take the form of electrical or magnetic signals capableof being stored, combined, compared, and/or otherwise manipulated. Ithas proven convenient at times, principally for reasons of common usage,to refer to these signals as bits, values, elements, symbols,characters, terms, numbers, and/or the like.

It should be borne in mind, however, that all of these and similar termsare to be associated with the appropriate physical quantities and aremerely convenient labels applied to these quantities. The presentdisclosure can refer to the action and processes of a computer system,or similar electronic computing device, that manipulates and transformsdata represented as physical (electronic) quantities within a computersystem's registers and memories into other data similarly represented asphysical quantities within the computer system's registers and memoriesor other such information-storage systems.

The present disclosure also relates to an apparatus for performing theoperations that are described herein. This apparatus can be speciallyconstructed for the intended purposes, or it can include ageneral-purpose computer selectively activated or reconfigured by acomputer program stored in the computer. Such a computer program can bestored in a computer-readable storage medium such as but not limited toany type of disk including floppy disks, optical disks, CD-ROMs,magnetic-optical disks, ROMs, RAMs, EPROMs, EEPROMs, magnetic or opticalcards, and/or any type of media suitable for storing electronicinstructions, each coupled to a computer system bus.

The algorithms and displays presented herein are not inherently relatedto any particular computer or other apparatus. Various general-purposesystems can be used with programs in accordance with the teachingsherein, or it can prove convenient to construct a more specializedapparatus to perform the method. The structure for a variety of thesesystems will appear as set forth in the present disclosure. In addition,the present disclosure is not described with reference to any particularprogramming language. It will be appreciated that a variety ofprogramming languages can be used to implement the teachings of thedisclosure as described herein.

The present disclosure can be provided as a computer program product, orsoftware, that can include a machine-readable medium having storedthereon instructions, which can be used to program a computer system (orother electronic device or devices) to perform a process according tothe present disclosure. A machine-readable medium includes any mechanismfor storing information in a form readable by a machine (e.g., acomputer). In some implementations, a machine-readable (e.g.,computer-readable) medium includes a machine-readable (e.g.,computer-readable) storage medium such as a ROM, RAM, magnetic diskstorage media, optical storage media, flash memory devices, and/or thelike.

In the foregoing specification, some example implementations of thedisclosure have been described. It will be evident that variousmodifications can be made thereto without departing from the broaderscope and spirit of the disclosure as set forth in the following claims.The specification and drawings are, accordingly, to be regarded in anillustrative sense rather than in a restrictive sense. Below is anon-exhaustive list of examples of implementations of the presentdisclosure.

Example 1 is a system that includes a plurality of memory components;and a processing device that is operatively coupled with the pluralityof memory components, the processing device including a host interface,an access management component, a media management component, and anMMC-restart manager that is configured to perform operations includingdetecting a triggering event for restarting the media managementcomponent; and, responsive to detecting the triggering event, performingMMC-restart operations including suspending operation of the accessmanagement component; determining whether the media management componentis operating, and if so then suspending operation of the mediamanagement component; resetting the media management component; resumingoperation of the media management component; and resuming operation ofthe access management component.

Example 2 is the subject matter of Example 1, where the triggering eventincludes receipt of a notification from the media management component.

Example 3 is the subject matter Example 2, where the notificationincludes a notification of an internal error of the media managementcomponent.

Example 4 is the subject matter of either Example 2 or Example 3, wherethe notification includes a notification of an error related to one ormore of the memory components in the plurality of memory components.

Example 5 is the subject matter of any of the Examples 1-4, where thetriggering event includes receipt of a notification of an error from afirmware of the system.

Example 6 is the subject matter of any of the Examples 1-5, where thetriggering event includes at least a threshold drop in a throughputlevel of the media management component.

Example 7 is the subject matter any of the Examples 1-6, where thetriggering event includes one or more uncorrectable data errors.

Example 8 is the subject matter of any of the Examples 1-7, wheresuspending operation of the access management component includessuspending acceptance by the access management component ofhost-interface traffic from the host interface.

Example 9 is the subject matter of any of the Examples 1-8, wheresuspending operation of the media management component includessuspending acceptance by the media management component ofaccess-management-component traffic from the access managementcomponent.

Example 10 is the subject matter of any of the Examples 1-9, where themedia management component includes a control path that includes (i)control-path memory and one or more rescuable registers and (ii) a datapath that includes a data buffer, and resetting the media managementcomponent includes clearing the control-path memory; clearing the one ormore resettable registers; and clearing the data buffer.

Example 11 is the subject matter of any of the Examples 1-10, theMMC-restart operations further including: after suspending operation ofthe access management component and prior to resuming operation of theaccess management component, determining whether there are any pendingcommands in the access management component, and if so then resetting astate of each pending command in the access management component; andrestarting each pending command in the access management component.

Example 12 is the subject matter of Example 11, where restarting eachpending command in the access management component includes restarting aplurality of pending commands in the access management component in anoriginal order.

Example 13 is the subject matter of Example 11, where the MMC-restartoperations further include reordering a plurality of pending commands inthe access management component into a revised order, and whererestarting each pending command in the access management componentincludes restarting the plurality of pending commands in the accessmanagement component in the revised order.

Example 14 is a method including detecting, by an MMC-restart manager ofa processing device, a triggering event for restarting a mediamanagement component of the processing device, the processing devicebeing operatively coupled with a plurality of memory components, theprocessing device further including a host interface and an accessmanagement component; and, responsive to detecting the triggering event,the MMC-restart manager performing MMC-restart operations includingsuspending operation of the access management component; determiningwhether the media management component is operating, and if so thensuspending operation of the media management component; resetting themedia management component; resuming operation of the media managementcomponent; and resuming operation of the access management component.

Example 15 is the subject matter of Example 14, where the triggeringevent includes receipt of a notification from the media managementcomponent.

Example 16 is the subject matter of either Example 14 or Example 15,where suspending operation of the access management component includessuspending acceptance by the access management component ofhost-interface traffic from the host interface.

Example 17 is the subject matter of any of the Examples 14-16, wheresuspending operation of the media management component includessuspending acceptance by the media management component ofaccess-management-component traffic from the access managementcomponent.

Example 18 is the subject matter of any of the Examples 14-17, where themedia management component includes (i) a control path that includescontrol-path memory and one or more rescuable registers and (ii) a datapath that includes a data buffer, and where resetting the mediamanagement component includes clearing the control-path memory; clearingthe one or more rescuable registers; and clearing the data buffer.

Example 19 is the subject matter of any of the Examples 14-18, where theMMC-restart operations further include: after suspending operation ofthe access management component and prior to resuming operation of theaccess management component, determining whether there are any pendingcommands in the access management component, and if so then resetting astate of each pending command in the access management component; andrestarting each pending command in the access management component.

Example 20 is a non-transitory machine-readable storage mediumcontaining instructions that, when executed by a processing device,cause the processing device to perform operations including detecting,by an MMC-restart manager of the processing device, a triggering eventfor restarting a media management component of the processing device,the processing device being operatively coupled with a plurality ofmemory components, the processing device further including a hostinterface and an access management component; and, responsive todetecting the triggering event, the MMC-restart manager performingMMC-restart operations including suspending operation of the accessmanagement component; determining whether the media management componentis operating, and if so then suspending operation of the mediamanagement component; resetting the media management component; resumingoperation of the media management component; and resuming operation ofthe access management component.

What is claimed is:
 1. A system comprising: a plurality of memorycomponents; and a processing device that is operatively coupled with theplurality of memory, components, the processing device comprising a hostinterface, an access management component, a media management component,and a media-management-component-restart manager that is configured toperform operations comprising: detecting a triggering event forrestarting the media management component; and responsive to detectingthe triggering event, performing media-management-component-restartoperations comprising: suspending operation of the access managementcomponent; determining whether the media management component isoperating, and if so then suspending operation of the media managementcomponent; resetting the media management component; resuming operationof the media management component; and resuming operation of the accessmanagement component.
 2. The system of claim 1, wherein the triggeringevent comprises receipt of a notification from the media managementcomponent.
 3. The system of claim 2, wherein the notification comprisesa notification of an internal error of the media management component.4. The system of claim 2, wherein the notification comprises anotification of an error related to one or more of the memory componentsin the plurality of memory components.
 5. The system of claim 1, whereinthe triggering event comprises receipt of a notification of an errorfrom a firmware of the system.
 6. The system of claim 1, wherein thetriggering event comprises at least a threshold drop in a throughputlevel of the media management component.
 7. The system of claim 1,wherein the triggering event comprises one or more uncorrectable dataerrors.
 8. The system of claim 1, wherein suspending operation of theaccess management component comprises: suspending acceptance by theaccess management component of host-interface traffic from the hostinterface.
 9. The system of claim 1, wherein suspending operation of themedia management component comprises: suspending acceptance by the mediamanagement component of access-management-component traffic from theaccess management component.
 10. The system of claim 1, wherein: themedia management component comprises: a control path that comprisescontrol-path memory and one or more resettable registers; and a datapath that comprises a data buffer; and resetting the media managementcomponent comprises: clearing the control-path memory; clearing the oneor more resettable registers; and clearing the data buffer.
 11. Thesystem of claim 1, the media-management-component-restart operationsfurther comprising: after suspending operation of the access managementcomponent and prior to resuming operation of the access managementcomponent, determining whether there are any pending commands in theaccess management component, and if so then: resetting a state of eachpending command in the access management component; and restarting eachpending command in the access management component.
 12. The system ofclaim 11, wherein restarting each pending command in the accessmanagement component comprises: restarting a plurality of pendingcommands in the access management component in an original order. 13.The system of claim 11, the media-management-component-restartoperations further comprising: reordering a plurality of pendingcommands in the access management component into a revised order,wherein restarting each pending command in the access managementcomponent comprises: restarting the plurality of pending commands in theaccess management component in the revised order.
 14. A methodcomprising: detecting, by a media-management-component-restart managerof a processing device, a triggering event for restarting a mediamanagement component of the processing device, wherein the processingdevice is operatively coupled with a plurality of memory components, andwherein the processing device further comprises a host interface and anaccess management component; and responsive to detecting the triggeringevent, the media-management-component-restart manager performingmedia-management-component-restart operations comprising: suspendingoperation of the access management component; determining whether themedia management component is operating, and if so then suspendingoperation of the media management component; resetting the mediamanagement component; resuming operation of the media managementcomponent; and resuming operation of the access management component.15. The method of claim 14, wherein the triggering event comprisesreceipt of a notification from the media management component.
 16. Themethod of claim 14, wherein suspending operation of the accessmanagement component comprises: suspending acceptance by the accessmanagement component of host-interface traffic from the host interface.17. The method of claim 14, wherein suspending operation of the mediamanagement component comprises: suspending acceptance by the mediamanagement component of access-management-component traffic from theaccess management component.
 18. The method of claim 14, wherein: themedia management component comprises: a control path that comprisescontrol-path memory and one or more rescuable registers; and a data paththat comprises a data buffer; and resetting the media managementcomponent comprises: clearing the control-path memory; clearing the oneor more resettable registers; and clearing the data buffer.
 19. Themethod of claim 14, the media-management-component-restart operationsfurther comprising: after suspending operation of the access managementcomponent and prior to resuming operation of the access managementcomponent, determining whether there are any pending commands in theaccess management component, and if so then: resetting a state of eachpending command in the access management component; and restarting eachpending command in the access management component.
 20. A non-transitorymachine-readable storage medium containing instructions that, whenexecuted by a processing device, cause the processing device to performoperations comprising: detecting, by amedia-management-component-restart manager of the processing device, atriggering event for restarting a media management component of theprocessing device, wherein the processing device is operatively coupledwith a plurality of memory components, and wherein the processing devicefurther comprises a host interface and an access management component;and responsive to detecting the triggering event, themedia-management-component-restart manager performingmedia-management-component-restart operations comprising: suspendingoperation of the access management component; determining whether themedia management component is operating, and if so then suspendingoperation of the media management component; resetting the mediamanagement component; resuming operation of the media managementcomponent; and resuming operation of the access management component.